Skip to content

fix: make row publication concurrency-safe by default - #45

Closed
pathscale wants to merge 1 commit into
masterfrom
fix/safe-mutation-publication
Closed

fix: make row publication concurrency-safe by default#45
pathscale wants to merge 1 commit into
masterfrom
fix/safe-mutation-publication

Conversation

@pathscale

Copy link
Copy Markdown
Owner

Closes #37
Closes #40

Summary

  • make immutable row-version publication mandatory for generated safe APIs, including no-default-feature builds
  • retain the former versioned-row-publication feature name as a compatibility no-op
  • revalidate generated point and range reads against current index mappings and defer link/page reuse until active readers drain
  • make delete return NotFound rather than panic in the staged insert publication window, with deterministic regression coverage
  • serialize Congee mutations because congee-wt 0.4.1 can lose disjoint structural insert/remove updates; native concurrent point reads remain unchanged

Verification

  • cargo fmt --all -- --check
  • cargo clippy --all-targets -- -D warnings
  • cargo test
  • cargo clippy --all-targets --no-default-features -- -D warnings
  • cargo test --no-default-features
  • cargo check --all-targets --features versioned-row-publication
  • Congee immediate disjoint insert/read/remove test: 100 consecutive focused passes

@pathscale

Copy link
Copy Markdown
Owner Author

Superseded by #46 (consolidated v1-blocker PR). Commits e39364c + 6515ba6 carried over.

@pathscale pathscale closed this Aug 4, 2026
@pathscale
pathscale deleted the fix/safe-mutation-publication branch August 9, 2026 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant